Thank you for submitting a Pull Request (PR) to the LLVM Project!

This PR will be automatically labeled and the relevant teams will be notified.

If you wish to, you can add reviewers by using the "Reviewers" section on this page.

If this is not working for you, it is probably because you do not have write permissions for the repository. In which case you can instead tag reviewers by name in a comment by using @ followed by their GitHub username.

If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers.

If you have further questions, they may be answered by the LLVM GitHub User Guide.

You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums.

It looks like you're trying to undo #106612? cc @mgorny

It looks like you're trying to undo #106612? cc @mgorny

Ah, not intentionally, I should have checked the git history more carefully before creating this PR (which is still only a draft). I don't use libscanbuild at all, but in OpenEmbedded builds the python modules are installed in the configured libdir which could be /usr/lib, /usr/lib32, /usr/lib64 and then they are packaged correctly, while libscanbuild didn't follow this and caused installed-vs-shipped QA issue (which basically means that something was installed in locations which aren't packaged by configured rules).

I believe the python code (d9cf829) should be fixed to look in the right install locations, but I'll leave that to someone actually using libscanbuild.

Sounds like a bug in OpenEmbedded then. CPython installs Python modules in /usr/lib, unconditionally.